Methods, systems, and products for security services

ABSTRACT

Methods, systems, and products notify of alarms in security systems. Sensor data is received from an alarm sensor, and an alarm controller determines an alarm condition. Video data associated with the alarm sensor is retrieved. An alarm message may be sent over a wireless network connection, while the video data may be sent over a wireline broadband connection.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/179,633 filed Feb. 13, 2014 and since issued as U.S. Pat. No.9,135,806, which is a continuation of U.S. application Ser. No.13/293,221 filed Nov. 10, 2011 and since issued as U.S. Pat, No.8,692,665, with both applications incorporated herein by reference intheir entireties.

BACKGROUND

Exemplary embodiments generally relate to communications and, moreparticularly, to alarm systems and to sensing conditions.

Security systems are common in homes and businesses. Security systemsalert occupants to intrusions. Security systems, though, may also warnof fire, water, and harmful gases.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

These and other features, aspects, and advantages of the exemplaryembodiments are better understood when the following DetailedDescription is read with reference to the accompanying drawings,wherein:

FIG. 1 is a simplified schematic illustrating an environment in whichexemplary embodiments may be implemented;

FIG. 2 is a schematic illustrating verification of alarms, according toexemplary embodiments;

FIG. 3 is a more detailed schematic illustrating a security system,according to exemplary embodiments;

FIG. 4 is a more detailed schematic illustrating receipt of an alarmmessage, according to exemplary embodiments;

FIGS. 5-6 are detailed schematics illustrating a verification call,according to exemplary embodiments;

FIG. 7 is a schematic illustrating bandwidth verification, according toexemplary embodiments;

FIGS. 8 and 9 are schematics illustrating cordless voice and telephonycapabilities, according to exemplary embodiments;

FIGS. 10-12 are schematics illustrating video data, according toexemplary embodiments;

FIGS. 13-15 are schematics illustrating data connectivity, according toexemplary embodiments;

FIG. 16 is a schematic illustrating a graphical user interface,according to exemplary embodiments;

FIG. 17 is a schematic illustrating remote verification, according toexemplary embodiments;

FIG. 18 is another schematic illustrating remote verification, accordingto exemplary embodiments;

FIGS. 19-20 are schematics further illustrating the security system,according to exemplary embodiments;

FIGS. 21-24 are schematics illustrating an alarm sensor, according toexemplary embodiments;

FIGS. 25-28 are schematics illustrating a takeover module, according toexemplary embodiments;

FIG. 29 is a schematic illustrating remote notification of the videodata, according to exemplary embodiments;

FIGS. 30 and 31 are schematics further illustrating remote notification,according to exemplary embodiments;

FIG. 32 is a schematic illustrating payment for emergency summons,according to exemplary embodiments;

FIG. 33 is a schematic illustrating an external antenna, according toexemplary embodiments;

FIG. 34 is a schematic illustrating an access portal, according toexemplary embodiments;

FIGS. 35-36 are schematics further illustrating the alarm controller andthe takeover module, according to exemplary embodiments;

FIGS. 37-40 are schematics further illustrating the alarm controller,according to exemplary embodiments;

FIGS. 41-43 are schematics further illustrating the alarm controller,according to exemplary embodiments;

FIGS. 44-49 are schematics further illustrating verification of alarms,according to exemplary embodiments;

FIGS. 50-51 are more schematics illustrating security services,according to exemplary embodiments; and

FIGS. 52-53 are schematics illustrating more operating environments,according to still more exemplary embodiments.

DETAILED DESCRIPTION

The exemplary embodiments will now be described more fully hereinafterwith reference to the accompanying drawings. The exemplary embodimentsmay, however, be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Theseembodiments are provided so that this disclosure will be thorough andcomplete and will fully convey the exemplary embodiments to those ofordinary skill in the art. Moreover, all statements herein recitingembodiments, as well as specific examples thereof, are intended toencompass both structural and functional equivalents thereof.Additionally, it is intended that such equivalents include bothcurrently known equivalents as well as equivalents developed in thefuture (i.e., any elements developed that perform the same function,regardless of structure).

Thus, for example, it will be appreciated by those of ordinary skill inthe art that the diagrams, schematics, illustrations, and the likerepresent conceptual views or processes illustrating the exemplaryembodiments. The functions of the various elements shown in the figuresmay be provided through the use of dedicated hardware as well ashardware capable of executing associated software. Those of ordinaryskill in the art further understand that the exemplary hardware,software, processes, methods, and/or operating systems described hereinare for illustrative purposes and, thus, are not intended to be limitedto any particular named manufacturer.

As used herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless expressly stated otherwise. Itwill be further understood that the terms “includes,” “comprises,”“including,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof. It will be understood thatwhen an element is referred to as being “connected” or “coupled” toanother element, it can be directly connected or coupled to the otherelement or intervening elements may be present. Furthermore, “connected”or “coupled” as used herein may include wirelessly connected or coupled.As used herein, the term “and/or” includes any and all combinations ofone or more of the associated listed items.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first device could be termed asecond device, and, similarly, a second device could be termed a firstdevice without departing from the teachings of the disclosure.

FIG. 1 is a simplified schematic illustrating an environment in whichexemplary embodiments may be implemented. A security system 100communicates with a central monitoring station 102 using a private datanetwork 104. The security system 100 has an alarm controller 106 thatreceives information from one or more alarm sensors 108. As those ofordinary skill in the art understand, the alarm sensors 108 monitor forheat, smoke, motion, gases, sound, or any other physical or logicalparameter that may indicate a security event. The alarm controller 106may also interface with one or more cameras 110 that capture video dataand microphones 112 that capture audio data. The cameras 110 andmicrophones 112 may constantly capture video and audio that isautomatically stored in a local mass storage device 114.

The security system 100 may wirelessly communicate with the private datanetwork 104. The private data network 104, for example, may have anaccess point name (or “APN”) 120 that identifies a wireless Internetprotocol packet data network that will be used to establish a wirelesscellular network connection 124 between the alarm controller 106 and theprivate data network 104. The security system 100 has a wirelesstransceiver 122 that uses the access point name 120 to communicate withthe private data network 104. The security system 100, for example, maysend and receive packets of data using a wireless carrier's 3G/LTE/4Gcellular network. The security system 100 may connect using a generalpacket radio service (GPRS), enhanced data rates for global evolution(EDGE), a universal mobile telecommunications service (UMTS), and/or ahigh speed packet access (HSPA). The wireless transceiver 122, however,may additionally or alternatively utilize any portion of theelectromagnetic spectrum and/or any communications standard orspecification (such as WI-FI®, BLUETOOTH®, or WI-MAX®). The access pointname 120 is a protocol that describes a configurable network identifierwhen connecting to the private data network 104. The access point name120 determines what type of network connection should be created, whatInternet protocol address(es) should be assigned to the security system100 (e.g., the wireless transceiver 122), and what security methodsshould be used. The access point name 120 may identify the Internetprotocol packet data network and the type of service that is provided bythe wireless Internet protocol packet data network.

The security system 100 provides security services. The security system100 monitors the inputs, status, or state of the alarm sensors 108, thecameras 110, and/or the microphones 112. When the security system 100detects an alarm condition 126, the security system 100 generates analarm message 128. The alarm message 128 is wirelessly sent to theaccess point name 120 and routed through the private data network 104 tothe central monitoring station 102. The alarm message 128, for example,may be received at a centralized alarm receiver server 130 and routed toa central monitoring station (“CMS”) server 132. The central monitoringstation server 132 may query an account database 134 to discoverdetailed customer information (as later paragraphs will explain). Thecentral monitoring station server 132 may then assign a human orcomputerized agent 136.

FIG. 2 is a schematic illustrating verification of alarms, according toexemplary embodiments. When the agent 136 is notified of the alarmmessage 128, the agent 136 may first verify the alarm condition 126. Asthe reader may understand, a high percentage of alarms are “false.” Thatis, alarms are often inadvertently triggered, such as when an owner of ahome opens a door and accidentally triggers an alarm. If the centralmonitoring station (“CMS”) server 132 were to immediately summon policeor fire services, but the alarm is false, then local police and firedepartments have wasted time and resources. Some municipalities may evenimpose fees for an unnecessary dispatch. One of the primary functions ofthe agent 136, then, is to first ascertain a true emergency beforesummoning emergency services.

The security system 100 may thus have two-way interactive voicecapabilities. The agent 136, for example, may establish a Voice-overInternet protocol (“VoIP”) call 140 with the security system 100. Theagent 136, for example, may call a telephone number or other addressassigned to the security system 100 and directly speak with an occupantof a home or business (as later paragraphs will explain). The Voice-overInternet protocol call 140 may also use the access point name 120associated with the private, wireless cellular network connection 124with the wireless transceiver 122. The Voice-over Internet protocol call140 may alternatively route over a wireline broadband connection to thealarm controller 106. The agent 136 may additionally or alternativelycall a designated number (such as a mobile phone) when alarms aredetected. The agent 136 may also retrieve audio and/or video data fromthe camera 110 and/or the microphone 112 (again, as later paragraphswill explain). The audio and/or video data may be live, real-time datacaptured by the cameras 110 and/or the microphones 112, but archivedaudio/video data may also be retrieved. The agent may thus speak with anoccupant, and view the audio and/or video data, to determine if thealarm condition 126 represents a true emergency. If the alarm is alegitimate security concern, then the agent 136 may notify localemergency services.

FIG. 3 is a more detailed schematic illustrating the security system100, according to exemplary embodiments. The alarm controller 106 has aprocessor 150 (e.g., “μP”), application specific integrated circuit(ASIC), or other component that executes a client-side securityapplication 152 stored in a memory 154. The client-side securityapplication 152 monitors the inputs, status, or state of the alarmsensors 108, the cameras 110, and/or the microphones 112. Theclient-side security application 152 may instruct any of the cameras 110and/or the microphones 112 to capture audio and/or video data. When theclient-side security application 152 detects the alarm condition 126,the client-side security application 152 instructs the processor 150 toretrieve an IP emergency alarm address (“IPEAA”) 156 from the memory124. The IP emergency alarm address 156 is a network communicationsaddress at which the centralized alarm receiver server 130 receivespacketized alarm messages from customers/subscribers of an alarmmonitoring service. The IP emergency alarm address 156 may be preloadedinto the memory 124, and the IP emergency alarm address 156 may bechanged after a software update to the client-side security application152.

The client-side security application 152 generates the alarm message128. The alarm message 128 includes data that identifies a networkaddress associated with the alarm controller 106. The alarm message 128may also include data that describes the alarm condition 126, such as analarm code associated with the sensor 108. The alarm message 128 mayalso include information describing the customer, such as a customeraccount code, physical street address, or other customer identifier.Whatever data is included in the alarm message 128, the data ispacketized according to a packet protocol. The alarm message 128 mayalso be encrypted to ensure privacy. Once the alarm message 128 isformatted and ready, the processor 150 commands the wireless transceiver122 to wirelessly send the alarm message 128.

The alarm message 128 routes through the private data network 104. Thealarm message 128 is sent to the access point name 120 associated withthe private, wireless cellular network connection 124 to the privatedata network 104. Packet headers are added or modified to route thealarm message 128 through the private data network 104 to the IPemergency alarm address 156 associated with the centralized alarmreceiver server 130. Because the private data network 104 is controlledand/or operated by a single carrier, the alarm message 128 is secure andnever encounters a publicly-available network segment.

The alarm message 128 may be encrypted and/or packetized using anypacket protocol. As those of ordinary skill in the art understand, thealarm message 128 may be packetized (or “framed”) for routing throughthe private data network 104. Information is grouped into packetsaccording to a packet protocol. As those of ordinary skill in the artalso understand, there are many packet protocols. Some of the morewell-known packet protocols include TCP/IP, IPX/SPX, AppleTalk, and SNA.Some standards organizations, such as the I.E.E.E., issue standards forpacketizing data. The private data network 104 may even utilize “mixed”protocols, where a translator determines the particular packet protocoland the appropriate destination for each packet. Because the basics ofpacketizing and packet protocols are well-known, this disclosure willnot further explain the packetizing of the alarm message 128.

FIG. 4 is a more detailed schematic illustrating receipt of the alarmmessage 128, according to exemplary embodiments. As the above paragraphsexplained, the alarm message 128 wirelessly routes from the alarmcontroller 106, through the private data network 104, and to thecentralized alarm receiver server 130. The centralized alarm receiverserver 130 may then route the alarm message 128 to the centralmonitoring station (“CMS”) server 132. The central monitoring stationserver 132 has a processor 170 (e.g., “μP”), application specificintegrated circuit (ASIC), or other component that executes aserver-side security application 172 stored in a memory 174. Theserver-side security application 172 and the client-side securityapplication 152 cooperate in a client-server environment to notify ofalarms from the security system 100.

When the central monitoring station server 132 receives the alarmmessage 128, the server-side security application 172 obtains any dataassociated with the alarm message 128. The server-side securityapplication 172, for example, may obtain the customer account codecontained in the alarm message 128 to retrieve customer accountinformation from the account database 134. The server-side securityapplication 172 may then pass the alarm condition 126 and any accountinformation on to the agent 136. The server-side security application172 may also retrieve a static, dynamic, and/or private network address176 associated with the alarm controller 106. The network address 176uniquely identifies the alarm controller 106 that generated the alarmmessage 128. The network address 176 may be retrieved from the accountdatabase 134, or the network address 176 may be extracted from one ormore header portions and/or payload portions of the packetized alarmmessage 128. However the network address 176 is obtained, theserver-side security application 172 knows the identity of the alarmcontroller 106 detecting the alarm condition 126. The server-sidesecurity application 172 may then assign the human or computerized agent136.

FIGS. 5-6 are detailed schematics illustrating a verification call,according to exemplary embodiments. Here the agent 136 directly callsthe alarm controller 106 to verify the alarm. Because the unique networkaddress 176 of the alarm controller 106 has been obtained, the agent 136may establish communication directly with the alarm controller 106. Theagent 136, for example, may establish the Voice-over Internet Protocolcall 140 to the alarm controller 106. The alarm controller 106 may havea Man-Machine Interface, such as a speaker 180, a microphone 182, and/ora keypad 184. The server-side security application 172 may also have aVoIP module 190 for conducting two-way voice communication. The agent136 may thus call the alarm controller 106 to verify the alarm condition126. The agent's speech may be output from the speaker 180, and theoccupant may speak into the microphone 182. The Voice-over InternetProtocol call 140 is thus enabled between the agent 136 and the occupantat the alarm controller 106. The agent 136 may require that the occupantauthenticate himself/herself, such as by entering a code or password onthe keypad 184. The occupant, however, may alternately speak a phrase toverify identity and/or the alarm condition 126. If the occupant verifiesthe alarm condition 126, then the agent 136 may summon emergencyservices.

The alarm controller 106 may only accept calls from predeterminedaddresses. Because the alarm controller 106 may receive calls, anyperson or party obtaining the unique network address 176 may call thealarm controller 106. The alarm controller 106 may thus be challenged bycalls from pranksters, telemarketers, and even friends and family. TheVoIP module 190 may thus be configured to only respond to calls from oneor more predetermined addresses 192. The VoIP module 190, for example,may be configured to only accept calls from addresses associated withthe central monitoring station 102, the central monitoring station(“CMS”) server 132, and/or the agent 136. When the alarm controller 106receives the Voice-over Internet Protocol call 140, the VoIP module 190may first compare a calling address (such as a calling telephone numberor a calling Internet Protocol address) to the predetermined addresses192. If the VoIP module 190 matches the calling address to thepredetermined addresses 192, then the VoIP module 190 may instruct thealarm controller 106 to accept the call. If the VoIP module 190 cannotobtain a match with the predetermined addresses 192, then the VoIPmodule 190 may instruct the alarm controller 106 to reject the call. TheVoIP module 190 may thus be configured to only accept calls from one ormore predetermined addresses 192.

FIGS. 5 and 6 also illustrate routing options for the Voice-overInternet Protocol call 140. FIG. 5 illustrates wireless routing over thewireless cellular network connection 124. The Voice-over Internetprotocol call 140 may route to the wireless transceiver 122 using theaccess point name 120 associated with the private, wireless cellularnetwork connection 124. When the agent 136 calls the unique networkaddress 176 of the alarm controller 106, the Voice-over InternetProtocol call 140 may route through the private data network 104, overthe wireless cellular network connection 124, and to the wirelesstransceiver 122.

FIG. 6 illustrates another routing option. The Voice-over InternetProtocol call 140 may route over a wireline broadband connection 200 tothe alarm controller 106. If the security system 100 has access to awireline broadband connection, then the alarm controller 106 may sendand receive data using a digital subscriber line modem, cable modem, orother gateway/modem device 202. When the agent 136 calls the uniquenetwork address 176 of the alarm controller 106, the Voice-over InternetProtocol call 140 may thus route over the wireline broadband connection200. FIG. 6 illustrates the Voice-over Internet Protocol call 140routing over the private data network 104 to the gateway/modem device202. FIG. 6, though, also illustrates that the Voice-over InternetProtocol call 140 may route at least partially over a public datanetwork 204 (such as the Internet of other distributed computingnetwork) to the gateway/modem device 202. Regardless, the gateway/modemdevice 202 then routes the Voice-over Internet Protocol call 140 to thealarm controller 106.

FIG. 7 is a schematic illustrating bandwidth verification, according toexemplary embodiments. Because the alarm controller 106 may have twosimultaneous communications paths to the security server 130, the alarmcontroller 106 may select the best routing option. That is, at any timethe alarm message 128 may be sent using either the wireless cellularnetwork connection 124 and/or the wireline broadband connection 200. Thealarm controller 106 may even receive the Voice-over Internet Protocolcall 140 using either the wireless cellular network connection 124and/or the wireline broadband connection 200. The client-side securityapplication 152 may thus include one or more performance thresholds 206and/or routing rules 208 that determine which routing path is preferred.The client-side security application 152, for example, may monitor andtrack or log bandwidth available from the wireless cellular networkconnection 124 and the wireline broadband connection 200. Theclient-side security application 152 may then compare bandwidthmeasurements to the performance thresholds 206 and select thecommunications path having the greatest bandwidth. If the wirelesscellular network connection 124 has a larger bandwidth value, then therouting rules 208 may require the wireless cellular network connection124 to send the alarm message 128 and/or to establish the Voice-overInternet Protocol call 140. If the wireline broadband connection 200 hasthe larger bandwidth value, then the routing rules 208 may cause theclient-side security application 152 to select the wireline broadbandconnection 200. This selection process may be repeated for eachcommunication to or from the alarm controller 106. This selectionprocess, in other words, may be repeated for the Voice-over InternetProtocol call 140, for remote notification, for polling messages, andfor connectivity messages (as later explained).

The performance thresholds 206 and/or routing rules 208, however, may bemore complex. While bandwidth is a useful and simple measure of networkperformance, other factors may also be collected and compared. Networkparameters measuring latency (delay), packet loss, and congestion may becollected to determine the best routing decision. Even urgency may beconsidered, such that the alarm message 128 has an urgent priority oftransmission. The video data 230, too, may be urgent, and the bandwidthmeasurements may determine the fastest delivery route. Other messages,though, may be less urgent and even routine (such as polling responsesor connectivity messages, explained later), so these messages may besent over a slower, but less expensive, communications path. Cost maythus be an important factor, for the wireless cellular networkconnection 124 and the wireline broadband connection 200 may havedifferent billing rates, access charges, and other incurred costs. Theclient-side security application 152 may thus evaluate networkperformance parameters to the performance thresholds 206 and select thepreferred communications path.

FIGS. 8 and 9 are schematics illustrating cordless voice and telephonycapabilities, according to exemplary embodiments. Here, when the agent136 calls the alarm controller 106 to verify the alarm condition 126,the call may route over the wireless cellular network connection 124and/or the wireline broadband connection 200 (as the above paragraphsexplained). Regardless, when the alarm controller 106 accepts the call,the call may be broadcast to one or more portable units 210 (such ascordless telephony handsets). The alarm controller 106 may thus havecordless voice and telephone capability to remotely communicate with theportable unit 210. As FIG. 8 illustrates, the alarm controller 106 mayinterface with a base station 212 that wirelessly communicates with eachportable unit 210. Each portable unit 210, for example, may be atelephony speakerphone handset that is installed throughout the home orbusiness. The client-side security application 152 may further havecode, programming, or instructions that cause the alarm controller 106to establish wireless telephony communication with the portable unit210. The base station 212 and the portable units 210, for example, maycommunicate according to the Digital Enhanced CordlessTelecommunications (or “DECT”) standard for cordless telephony and voicemonitors. When the agent 126 calls the alarm controller 106, the VoIPmodule 190 may cause the alarm controller 106 to enter an off-hook modeof operation and automatically answer the Voice-over Internet Protocolcall 140. The base station 212 may thus broadcast the Voice-overInternet Protocol call 140 to the one or more portable units 210 (i.e.,speakerphone handsets) to provide two-way interactive voicecommunication. An occupant and the agent 126 may conduct a two-way voiceconversation to access the emergency. Because the base station 212 mayautomatically answer the Voice-over Internet Protocol call 140, anyoccupants need not find the portable unit 210 and physically answer thecall. The occupant need only speak to verify the emergency. Theautomatic answering feature also enables the agent to listen to what isoccurring in the residence. If an occupant fails to speak and verify,the agent 126 may simply listen to ambient sounds for verification. Thebase station 212 and the portable units 210, however, may alsocommunicate using any of the IEEE 802 family of standards (such asBLUETOOTH® or WI-FI®).

The base station 212 may execute broadcast rules 214. Because the alarmcontroller 106 may only accept calls from the predetermined addresses192, the broadcast rules 214 may define how the base station 212transmits calls to the one or more portable units 210. The base station212, in other words, may selectively transmit calls based on thepredetermined addresses 192 and/or the broadcast rules 214. When thealarm controller 106 receives the Voice-over Internet Protocol call 140,the VoIP module 190 may first compare the calling address (e.g., thecalling telephone number or the calling Internet Protocol address) tothe predetermined addresses 192 (as earlier paragraphs explained). Ifthe calling address is matched to the predetermined addresses 192, thenthe VoIP module 190 may also retrieve the broadcast rule 214 that isassociated with the calling address. Different broadcast rules 214 maybe stored in the memory of the alarm controller 106, and each broadcastrule 214 determines how the base station 212 broadcasts the Voice-overInternet Protocol call 140.

FIG. 9 illustrates the broadcast rules 214. The broadcast rules 214 maydefine to which portable unit 210 the call is transmitted. Because theremay be multiple portable units 210 installed throughout the home orbusiness, each portable unit 210 may have a unique wireless address 216.Each portable unit 210, in other words, may be uniquely addressed usingthe corresponding wireless address 216 assigned to each portable unit210. FIG. 9 illustrates the broadcast rules 214 as a table 218 thatmaps, relates, or calling addresses 220 to wireless addresses 216. Thebroadcast rules 214, however, may have any logical expression orstructure that determines how calls are processed to the portable units210. Regardless, the client-side security application 152 queries forthe wireless address(es) 220 associated with the calling address 220.The client-side security application 152 retrieves the wirelessaddress(es) 220 and instructs the base station 212 to send theVoice-over Internet Protocol call 140 to those wireless address(es) 220.Exemplary embodiments thus permit the Voice-over Internet Protocol call140 to be broadcast to a single portable unit 210, or to multipleportable units 210, per the broadcast rules 214. Because each portableunit 210 is addressable, the Voice-over Internet Protocol call 140 maynot be transmitted to a particular portable unit 210, per the broadcastrules 214. Calls from the agent 136, for example may be transmitted toall the portable units 210 to ensure the occupant answers the call 140using any of the portable units 210. If the call is from a familymember, then perhaps the call is only transmitted to some of theportable units 210. The broadcast rules 214 may thus be defined as bestsuits the occupant.

The base station 212 and the portable units 210 aid in verification ofalarms. During the alarm condition 126, the agent 136 at the centralmonitoring station 102 calls the alarm controller 106 to verify thealarm. The VoIP module 190 may use session initiation protocol (SIP) andinstruct the base station 212 to auto-answer the incoming Voice-overInternet Protocol call 140 and to command one, or more, portable units210 to go off-hook. Then agent 136 begins speaking through the portableunits 210 with an occupant to verify the alarm.

The base station 212 and the portable units 210 also provide an intercomfeature. Because the base station 212 wirelessly communicates with theportable units 210, these components also provide two-wayintercommunications throughout the home or business. During non-alarmconditions the portable units 210 may be used as intercom speakerphoneunits to communicate with an occupant at the base station 212 and/oralarm controller 106.

FIGS. 10-12 are schematics illustrating video data 230, according toexemplary embodiments. When the alarm controller 106 detects the alarmcondition 126, exemplary embodiments may also capture and/or retrievevideo data 230 of the possible intrusion, fire, or other emergency. AsFIG. 10 illustrates, the client-side security application 152 may querya database 232 of video data. The database 232 of video data stores thevideo data 230 captured from the cameras 110 in the home or business.The video data 230 may be real-time or archived. Because there may bemultiple cameras 110 in the home or business, exemplary embodiments mayselect the camera 110 that best provides video of the possibleemergency. Camera #1, for example, may be trained or aimed on thekitchen door, while camera #2 captures a front entry door. Cameras maybe installed throughout the home or business to provide views of manywindows, doors, and other locations. If a camera is motorized to panand/or to zoom, then the camera 110 may also have multiple orientationsfor multiple views. FIG. 10 illustrates the database 232 of video dataas a table 234 that maps, relates, or associates alarm sensors 108 tocamera addresses 236. The database 232 of video data may thus storerelationships that best capture the video data 230 of an area associatedwith the alarm sensor 108. When the client-side security application 152queries the database 232 of video data for the alarm sensor 108, theclient-side security application 152 may also retrieve the correspondingcamera address 236. Because there may be multiple cameras throughout ahome or business, each camera may be uniquely identified by the cameraaddress 236 (such as a public or private Internet Protocol address).Once the camera address 236 is known, exemplary embodiments may obtainthe corresponding video data 230 to further verify the intrusion.

FIG. 11 illustrates the video data 230. The agent 136 at the centralmonitoring station 102 may send a video request 240 instructing thealarm controller 106 to retrieve and send the video data 230 captured bythe camera 110 associated with the alarm sensor 108. When the alarmcontroller 106 receives the video request 240, the client-side securityapplication 152 retrieves the live and/or archived video data 230associated with the corresponding camera address 236. The alarmcontroller 106 sends the relevant video data 230 to some network address(such as the agent's computer terminal 242). The agent 136 may thus viewthe video data 230 to help verify the intrusion.

The video data 230, however, may be automatically sent. When the alarmcontroller 106 detects the alarm condition 126, the client-side securityapplication 152 may be programmed or configured to automatically sentthe video data 230. This automatic response may be desired whenbandwidth is not a concern, such as holidays or hours when the datanetwork 104 is uncongested. The client-side security application 152 maythus automatically retrieve and send the video data 230 whenever thealarm condition 126 is detected. When the alarm condition 126 isdetected, the client-side security application 152 may automaticallyquery for the camera address 236 associated with the alarm sensor 108.The client-side security application 152 retrieves the video data 230from the camera 110 at the camera address 236. The client-side securityapplication 152 may then send the video data 230 to accompany the alarmmessage 128.

The amount of the video data 230, however, may be limited. If a largeamount of the video data 230 is automatically retrieved and sent,chances are high that delivery will be delayed or even fail. The videodata 230 may be bandwidth intensive, so the wireless cellular networkconnection 124 may congest and delay or fail. Exemplary embodiments maythus only send, or stream, a specified amount or duration of the videodata 230 (such as ten seconds). This video data 230 may be automaticallybuffered (perhaps on a first in, and first out basis) in the memory ofthe alarm controller 106 and/or in the mass storage device 114 (as FIG.1 illustrated). If the home or business has multiple cameras, then thevideo data 230 from each camera 110 may be stored. During the alarmcondition 126 the alarm controller 106 streams a snippet of the videodata 230 (perhaps via fttp) to the central monitoring station (“CMS”)server 132. The agent 136 is notified that the video data 230 isavailable for verification. Because the video data 230 may be bufferedon a continuous basis, the alarm controller 106 may retrieve and streampre-alarm and post-alarm video data. That is, five seconds of video data230 captured before the alarm condition 126 may be sent, along with fiveseconds captured after the alarm condition 126 is detected. The agent136 may even have permission to access live video data.

The agent 136 (perhaps at the agent's computer terminal 242) may requestvideo from any camera 110. As the agent 136 attempts to verify thealarm, the agent may select any of the cameras 110 in the home orbusiness and receive streaming video data 230. The agent's computerterminal 242 may even display information indicating the camera, camerazone, and/or the alarm condition 126. The agent's computer terminal 242may also display a graphical user interface that permits the agent 136to access the live video data 230 from any camera 110 in the home orbusiness. Under most circumstances the agent 136 will receive and viewthe live video data 230 from one camera 110 at a time. If bandwidthpermits, though, the agent may select and view live video data 230 frommultiple cameras 110 at one time. The live video data 230 will notcreate congestion in the private data network 104, so the onlycongestion may occur in the customer's access network (e.g., thewireless cellular network connection 124 and/or the wireline broadbandconnection 200). For example, if a customer has a wireline broadbandADSL service with 1.5 Mbps downstream and 256 Kbps upstream, theupstream bandwidth could be limiting.

The agent 136 may search the video data 230. The alarm controller 106may interface with the mass storage device 114 (as FIG. 1 illustrated).The alarm controller 106 may thus locally archive streaming video data230 from the cameras 110 in the home or business. The agent 136 may thusaccess search functions that permit locating the video data 230 outputby a particular camera 110.

FIG. 12 illustrates a dedicated communications path for the video data230. As this disclosure earlier explained, the alarm controller 106 mayhave two communications paths to the security server 130. The alarmcontroller 106 may send and receive data over the wireless cellularnetwork connection 124. The alarm controller 106, however, may also sendand receive data over the wireline broadband connection 200. Exemplaryembodiments may thus be configured to always prefer one or the othercommunications path. Exemplary embodiments, for example, may prefer thewireless cellular network connection 124 for the alarm message 128, butthe wireline broadband connection 200 is preferred when sending thevideo data 230. Even though the alarm controller 106 may always send thealarm message 128 over the wireless cellular network connection 124, thealarm controller 106 may decline the wireless cellular networkconnection 124 for the video data 230. The video data 230 may burden thewireless cellular network connection 124, thus denying the agent 136high-quality video data for security purposes. Indeed, the video data230 may cause congestion in a wireless network, and delivery may eventimeout or fail. When the video data 230 is sent from the alarmcontroller 106, the client-side security application 152 may retrieveand execute a video rule 250. The video rule 250 instructs or forces thealarm controller 106 to automatically route the video data 230 over thewireline broadband connection 200 to avoid congesting the wirelessaccess point 120.

FIGS. 13-15 are schematics illustrating data connectivity, according toexemplary embodiments. Here the central monitoring station 102 maycontinuously monitor data connectivity to the alarm controller 106. Ifthe central monitoring station 102 cannot communicate with the alarmcontroller 106, the essential security functions have failed. Thecentral monitoring station 102 may thus monitor data connectivity toensure either the wireless cellular network connection 124 or thewireline broadband connection 200 is always available.

FIG. 13 illustrates polling messages 260 that are sent from the centralmonitoring station 102. The central monitoring station 102 (e.g., thecentralized alarm receiver server 130 and/or the central monitoringstation (“CMS”) server 132) may continuously or periodically send apolling message 260 (or “ping”) to the alarm controller 106. Eachpolling message 260 allows the central monitoring station 102 torandomly or periodically determine the status of the wireless cellularnetwork connection 124 and the wireline broadband network connection200. If the alarm controller 106 responds, then connectivity issuccessful. Exemplary embodiments may thus poll for the availability ofeach simultaneous network connection 124 and 200. If a “ping” isunsuccessful, then a trouble condition may be automatically reported toa network operations center 262. Personnel in the network operationscenter 262 will then identify and isolate the trouble. A trouble ticket264 may be automatically generated to restore service.

Each polling message 260 may specifying routing. When the pollingmessage 260 is sent, the polling message 260 may specify thecommunications path to be used. That is, the headers and/or payload of apacket may require routing over either the wireless cellular networkconnection 124 or over the wireline broadband network connection 200. Ifa response is received from the alarm controller 106, then the securityserver 130 knows the respective communications path is functioning.

FIG. 14 illustrates a self-reporting feature. Here the alarm controller106 may self-report its connectivity to the central monitoring station102. That is, the client-side security application 152 causes the alarmcontroller 106 to automatically send a connectivity message 270 to thecentralized alarm receiver server 130 and/or the central monitoringstation (“CMS”) server 132). A first connectivity message 270, forexample, is sent over the wireless cellular network connection 124,while a second connectivity message 270 is sent over the wirelinebroadband network connection 200. If the central monitoring station 102receives either connectivity message 270, then the security server 130knows the respective communications path is functioning.

The self-reporting feature illustrated in FIG. 14 reduces traffic. Ifthe polling message 260 is sent, the alarm controller 106 sendsresponses. This poll-and-response technique thus adds significanttraffic to the data network 104, and responses from many securitysubscribers may congest the data network 104. The self-reporting featureof FIG. 14, though, reduces traffic by half. Because each alarmcontroller 106 may self-report the connectivity message 270, thesecurity server 130 need not respond. That is, as long as the centralmonitoring station 102 receives each connectivity message 270, thecentral monitoring station 102 knows the respective communications pathis functioning. No response need be sent, so the self-reporting featureof FIG. 14 reduces traffic by half.

FIG. 14 also illustrates connectivity rules 272. Here the connectivityrules 272 may define how often the alarm controller 106 self-reportsitself to the central monitoring station 102. As the client-sidesecurity application 152 executes the connectivity rules 272, theconnectivity rules 272 cause the client-side security application 152 tosend the connectivity messages 270. The connectivity rules 272 cause theconnectivity messages 270 to be sent over both the wireless cellularnetwork connection 124 and over the wireline broadband networkconnection 200. Each connectivity message 270 identifies either thewireless cellular network connection 124 or the wireline broadbandnetwork connection 200, thus identifying the communications path overwhich the connectivity message 270 is routed. A header or payload of apacket, for example, may identify either the wireless cellular networkconnection 124 or the wireline broadband network connection 200. Theconnectivity rules 272 may thus define how often the connectivitymessages 270 are sent from the alarm controller 106.

The connectivity rules 272 may be defined or configured. Businesscustomers, for example, may have higher liability and security concerns,so the connectivity rules 272 may require more frequent connectivitymessages 270 than residential customers. A timer 274 may thus beinitialized that defines the frequency of each connectivity message 270.When the timer 274 counts down to a final value, another connectivitymessage 270 is sent. The connectivity rules 272 and/or the timer 274 maybe defined or configured to specify how frequently the connectivitymessages 270 are sent, and over which communications path (e.g., thewireless cellular network connection 124 and/or the wireline broadbandnetwork connection 200) is used. As an example, commercial/businesscustomers may require confirmation of connectivity at least every 200seconds to verify a single communications connection, but the dual-pathroute (e.g., the wireless cellular network connection 124 and/or thewireline broadband network connection 200) may only require confirmationevery 300 seconds. Residential customers may be content withconfirmation of connectivity at least once per month, once per day, oreven hourly. If the central monitoring station 102 fails to receive aconnectivity message 270, the central monitoring station 102 may thensend the polling message 260 (as FIG. 13 illustrated) as a back-upverification process. If no response is received, then a troublecondition may be automatically reported to the network operations center262.

FIG. 15 illustrates more verification procedures. If the centralmonitoring station 102 determines one of the communications paths isdown, procedures may be implemented to require the other communicationspath. For example, if the wireless cellular network connection 124 isunavailable, the central monitoring station 102 will not receive aresponse to the polling message 260 sent over the wireless cellularnetwork connection 124. The central monitoring station 102 may thus senda configuration command 280 to the alarm controller 106. Because thewireless cellular network connection 124 is unavailable, the centralmonitoring station 102 routes the configuration command 280 over thewireline broadband network connection 200. The configuration command 280changes the configuration parameters in the client-side securityapplication 152 to always utilize the available wireline broadbandnetwork connection 200 until further instructed. That is, theclient-side security application 152 is instructed to route future alarmmessages 128 over the available wireline broadband network connection200. Conversely, if wireline broadband network connection 200 isunavailable, the configuration command 280 instructs the client-sidesecurity application 152 to send the video data (illustrated asreference numeral 230 in FIG. 12) over the wireless cellular networkconnection 124 until further instructed. If the video data 230 causestoo much congestion, though, the alarm controller 106 may be instructedto disregard the video request (illustrated as reference numeral 240 inFIG. 11) and/or to decline to send the video data 230. When service isrestored, another configuration command 280 may be sent to restore theconfiguration parameters in the client-side security application 152.

FIG. 16 is a schematic illustrating a graphical user interface 290,according to exemplary embodiments. The graphical user interface 290 maybe produced on the agent's computer terminal 242 to help verify alarms.When an alarm is detected, the customer's security system 100 sends thealarm message 128 to the centralized alarm receiver server 130. Thealarm message 128 routes to the central monitoring station (“CMS”)server 132 and the agent 136 is selected to verify the alarm beforesummoning emergency services. As FIG. 16 illustrates, the graphical userinterface 290 may help the agent 136 verify the alarm. The graphicaluser interface 290 is displayed by a display device and visuallypresents verification information. The graphical user interface 290, forexample, may display a floor plan 292 of the customer's residence orbusiness, along with an overlay of the alarm sensors 108. That is, thegraphical user interface 290 may map a location of each alarm sensor 108onto the floor plan 292. Digital pictures 294 of the home or businessmay be included, along with pictures of the occupants. GlobalPositioning System (GPS) coordinates 296 may also be displayed for thealarm sensors 108 and/or other physical features. The video data 230 mayalso be presented to further aid the agent 136.

FIG. 17 is a schematic illustrating remote verification, according toexemplary embodiments. If the Voice-over Internet Protocol call 140 tothe alarm controller 106 is unanswered, remote verification may beauthorized. The server-side security application 172 may thus attempt tonotify one or more other addresses when the alarm condition 126 isdetected. As FIG. 17 illustrates, the server-side security application172 may query for one or more notification addresses 300. Eachnotification address 300 is any communications address which is notifiedof alarms detected by the alarm controller 106. The server-side securityapplication 172 may query a notification table 302 for the notificationaddress(es) 300. FIG. 17 illustrates the notification table 302 storedin the central monitoring station (“CMS”) server 132, but thenotification table 302 may be remotely located and accessed from anylocation or device in the data network 104 and/or in the public datanetwork 204. The notification table 302 associates some customerinformation 306 to the notification addresses 300. The customerinformation 306 may be any information that uniquely identifies thecustomer, such as a customer code, physical address, name, or even thenetwork address 176 assigned to the alarm controller 106. Once thecustomer information 306 is obtained from the account database 134, theserver-side security application 172 queries the notification table 302for the customer information 306. The notification table 302 returns thenotification address(es) 300 approved for remote notification. Eachnotification address 300 may be a telephone number, email address, otherInternet Protocol address, or any other communications address to whichnotifications are sent. Indeed, multiple notification addresses 300 maybe associated to the network address 176 of the alarm controller 106.Exemplary embodiments may thus retrieve a list 308 of notificationaddresses. Each entry in the list 308 of notification addresses may be atelephone number, Internet Protocol address, email address, and/or anyother communications address.

An alarm notification 310 is then sent. The server-side securityapplication 172 causes the central monitoring station (“CMS”) server 132to format the alarm notification 310 and to send the alarm notification310 to each entry in the list 308 of notification addresses. The alarmnotification 310 may be an electronic message, such as a text message oremail message. The alarm notification 310, however, may also be ananalog telephone call or a Voice-over Internet Protocol call.Regardless, the alarm notification 310 may include informationdescribing the alarm condition 126 (such as the alarm sensor 108, thecustomer information 306, a physical street address of the alarmcontroller 106, and/or any other information). The alarm notification310 routes through the data network 104 and/or the public data network204 to a third party communications device 312 associated with one ofthe notification addresses 300. If the alarm notification 310 involvesanalog telephony, the alarm notification 310 may also route along someportion of a public-switched telephony network. The server-side securityapplication 172 may thus notify friends, neighbors, a spouse, children,and any communications addresses in the list 308 of notificationaddresses.

FIG. 18 is another schematic illustrating remote verification, accordingto exemplary embodiments. Here the alarm controller 106 itself maynotify others when alarms are detected. When the alarm controller 106detects the alarm condition 126, the client-side security application152 may access the notification address 300 that is approved for remotenotification. FIG. 18 illustrates the notification address 300 as beinglocally stored in the alarm controller 106, perhaps associated with aprofile 320 of the occupant or home/business. If multiple notificationaddresses 300 are approved for remote notification, then the list ofnotification addresses (illustrated as reference numeral 308 in FIG. 17)may be retrieved. The client-side security application 152 formats thealarm notification 310 and sends the alarm notification 310 to eachnotification address 300 approved for remote notification. The alarmnotification 310 may again include any information (such as the alarmsensor 108, the customer information 306, and/or the physical streetaddress of the alarm controller 106). FIG. 18 illustrates the alarmnotification 310 routing to the recipient at the third partycommunication device 312.

FIGS. 19-20 are schematics further illustrating the security system 100,according to exemplary embodiments. Here the residential or businesssecurity system 100 need not include a broadband modem. That is, thealarm controller 106 may simply plug-in, or interface to, the existingcable, digital subscriber line (DSL), or other gateway/modem device 202.FIG. 19, for example, illustrates a cable (e.g., CAT 5, 6, or 7)interconnecting a port of the occupant's existing gateway/modem device202 to the alarm controller 106. FIG. 20 illustrates an alternativepowerline interface 330 (such as HOMEPLUG®) that allows the occupant'sexisting gateway/modem device 202 to interface with the alarm controller106. Exemplary embodiments thus allow the alarm controller 106 to bedeployed in any home or business, regardless of the gateway/modem device202 (e.g., ADSL, VDSL, GPON, and bring-your-own broadband).

FIGS. 21-24 are schematics illustrating the alarm sensor 108, accordingto exemplary embodiments. Here each alarm sensor 108 may have a wirelessinterface 360 to the alarm controller 106. Conventional security systemsuse wired sensors to detect security events. Wired sensors, though, aredifficult to install, often requiring specialized installations androutings of wires. Exemplary embodiments may thus utilize the wirelessinterface 360 for easier and cheaper installations.

FIG. 21 is a block diagram of the alarm sensor 108. The alarm sensor 108has a parameter detector 362 that detects or senses some physical orlogical parameter (such as temperature, smoke, motion, or sound). Asensor processor 364 commands the wireless interface 360 to wirelesslysend or broadcast sensor data 366. The sensor data 366 is wirelesslyreceived by the alarm controller 106. The wireless transceiver 122 inthe alarm controller 106, for example, may wirelessly receive the sensordata 366 sent from the alarm sensor 108. The client-side securityapplication 152 obtains the sensor data 366 and compares the sensor datato one or more rules 368 and threshold values 370 stored in the alarmcontroller 106. If the sensor data 366 indicates a security event, thealarm condition 126 is determined and the alarm message 128 is sent tothe central monitoring station 102 (as earlier paragraphs explained).While the alarm sensor 108 may have an alternating current (AC) powersource 372, a battery 374 may be included.

FIG. 22 further illustrates the wireless interface 360. Here thewireless interface 360 may only have one-way transmission capability topreserve battery life. That is, the alarm sensor 108 may only send thesensor data 366 to the alarm controller 106. A sensor transmitter 380may thus lack capability to receive data or information to conserve thelife of the battery 374. Because the alarm sensor 108 may only transmitthe sensor data 366, electrical power from the battery 374 is notconsumed for wireless reception. Even though the sensor transmitter 380may utilize any portion of the electromagnetic spectrum, exemplaryembodiments may utilize a proprietary portion (such as 433 MHz) of theelectromagnetic spectrum. The sensor processor 364 executes a sensorprogram 382 stored in memory 384 of the alarm sensor 108. The sensorprogram 382 causes the sensor processor 364 to only broadcast the sensordata 366 during an alarm. Even though the alarm sensor 108 maycontinuously, periodically, or randomly monitor or measure the sensordata 366, the alarm sensor 108 may only transmit the sensor data 366that equals or exceeds some threshold value 386. The sensor transmitter380 may thus only consume electrical power from the battery 374 when thesensor data 366 necessitates.

FIG. 23 further illustrates the wireless interface 360. Here the alarmsensor 108 may broadcast its health and identity. That is, the sensorprogram 382 may randomly or periodically execute a diagnostic routine390, such as every seventy (70) minutes. The sensor transmitter 380 maythen wirelessly send a diagnostic result 392, along with a sensoridentifier 394 associated with the alarm sensor 108. The sensoridentifier 394 may be any alphanumeric combination that uniquelyidentifies the alarm sensor 108 from other alarm sensors. When the alarmcontroller 106 receives the diagnostic result 392 and the sensoridentifier 394, the client-side security application 152 may compare thediagnostic result 392 to a diagnostic range 396 of values. If thediagnostic result 392 satisfies the diagnostic range 396 of values, thenthe alarm sensor 108 is assumed to be properly functioning. If thediagnostic result 392 fails to satisfy the diagnostic range 396 ofvalues, then a fault 398 may be assumed and the alarm controller 106 mayflag and/or display an error 400 associated with the sensor identifier394.

The one-way wireless interface 360 may be best suited to magneticsensors. As those of ordinary skill in the art have known, many securitysystems utilize magnetic sensors for doors and windows. When a door orwindow opens, a magnet (not shown) pulls away from a metal strip orcontact. As the magnet pulls away, the magnet electromagneticallydecouples, thus opening like a switch in a circuit. The alarm sensor 108thus simply detects low or no current, voltage, or continuity as thedoor or window opens. The sensor program 382 may thus cause the sensorprocessor 364 and the sensor transmitter 380 to broadcast the sensordata 366 (e.g., low or no current, voltage, or continuity) only when themagnet pulls away from the door or window. The one-way transmissioncapability of the wireless interface 360 may thus be effectively usedfor windows and doors, where the life of the battery 374 may be extendedthree to five years.

FIG. 24 illustrates two-way capability. Here the wireless interface 360may both send and receive, thus bi-directionally communicating with thealarm controller 106. FIG. 24, for example, illustrates aninitialization of the alarm sensor 108. The alarm sensor 108 mayresponse to a command 410 sent in a message 412 from the alarmcontroller 106. The command 410 may instruct the alarm sensor 108 toturn on, to awaken, or to respond. The message 412 may also include asensor address 414, thus permitting different alarm sensors 108 to beindividually addressed and activated/deactivated. When the alarm sensor108 receives the message 412, the alarm sensor 108 executes the command410, as instructed by the alarm controller 106. The alarm sensor 108 mayrespond by sending the sensor data 366 to the alarm controller 106. Thealarm sensor 108 may also broadcast its diagnostic result 392 and thesensor identifier 394 to indicate its health and identity (as the aboveparagraph explained). When the alarm sensor 108 has two-way capability,the sensor transmitter 380 may again utilize any portion of theelectromagnetic spectrum, such as the 900 MHz spectrum. This two-waycapability consumes more electrical power from the battery 374, so thetwo-way capability may be reserved for keypads and for sensors that areeasily accessed for battery replacement.

FIGS. 25-27 are schematics illustrating a takeover module 420, accordingto exemplary embodiments. The takeover module 420 allows exemplaryembodiments to be retrofitted to one or more existing wired sensors 422and/or wired contacts 424. As earlier paragraphs explained, conventionalsecurity systems have long used the wired contacts 322 and sensors 324to detect security events. Because these existing wired sensors 422 andcontacts 424 may still adequately function for basic security services,some customers may not want to incur added costs to tear-out aged, butfunctioning, components. The takeover module 420 thus allows the alarmcontroller 106 to interface with existing wired keypads, sirens, andsensors in older installations. An existing controller may be removed,and the existing alarm zones, or circuits 426, may be interfaced to thealarm controller 106. The takeover module 420 thus permits oldersecurity systems to be up-fitted without incurring substantialinstallation costs.

As FIG. 26 illustrates, the takeover module 420 has one or more terminalstrips 430 of pairs 432 of terminals. An existing pair 434 of wires fromthe existing window contact 424 is connected to a first pair 436 ofterminals in the takeover module 420. A second existing pair 438 ofwires from the existing sensor 422 is connected to a second pair 440 ofterminals. If multiple circuits serve multiple existing securitycomponents, then each corresponding pair of wires is connected to adifferent pair 432 of terminals in the takeover module 420. A differentpair 432 of terminals, in other words, is connected to each two-wirepair in a security circuit 426. The takeover module 420 may also have asocket 450 for connection to an existing keypad 452. The takeover module420 applies an electrical current to each pair 432 of terminals. Theelectrical current flows through the existing circuits 426 and returnsback to each respective pair 432 of terminals in the takeover module420. As earlier paragraphs explained, when a window or door is opened,the corresponding wired component (e.g., the existing sensor 422 or theexisting window contact 424) creates an open-circuit condition. When thecircuit 426 opens, the takeover module 420 detects no current betweenthe corresponding pair 432 of terminals. The takeover module 420 thusreports an open-circuit condition 454 to the alarm controller 106, alongwith a terminal identifier 456 associated with the open circuit.

As FIG. 27 illustrates, exemplary embodiments may thus detect intrusionevents. When an open circuit is detected, the alarm controller 106receives the open-circuit condition 454 and the terminal identifier 456.The client-side security application 152 may then query an intrusiondatabase 460. FIG. 27 illustrates the intrusion database 460 stored inthe memory 154 of the alarm controller 106, but the intrusion database460 may be stored in the takeover module 420 or remotely accessed fromthe data network (illustrated as reference numeral 104 in FIG. 1).Regardless, the intrusion database 460 is illustrated as a table 462that maps, relates, or associates terminal identifiers 456 to circuitdescriptors 464. Each circuit descriptor 464 may be a textualdescription of an existing sensor circuit (illustrated as referencenumeral 426 in FIGS. 25 & 26). The intrusion database 460 thus providesa simple description of a possible intrusion event, such as “masterbedroom window open” or “garage door open.” The client-side securityapplication 152 queries the intrusion database 460 for the terminalidentifier 456 in the open-circuit condition 454 detected by thetakeover module 420. The client-side security application 152 retrievesthe corresponding circuit descriptor 464 and sends the alarm message 128to the central monitoring station 102 (as earlier paragraphs explained).The alarm message 128 may thus include a textual description of thesecurity event (such as “glass breakage in garage” or “kitchen dooropen”). Should the central monitoring station (“CMS”) server 132 sendthe alarm notification (illustrated as reference numeral 310 in FIGS.17-18) for remote notification, the alarm notification 310 may,likewise, include the textual description of the security event.

FIG. 28 is a block diagram of the takeover module 420, according toexemplary embodiments. The takeover module 420 has a voltage source 470that applies a voltage V_(O) (illustrated as reference numeral 472) to avoltage strip 474. Each pair 432 of terminals in the takeover module 420has one terminal electrically connected to the voltage strip 474 and asecond terminal electrically connected to electrical ground 476. Thevoltage V_(O), for example, is applied to a first terminal 478 in thepair 432 of terminals, while a second terminal 480 is connected toelectrical ground 476. Because the existing wires 434 and the existingwired contact 424 electrically resemble a resistance 482 (as may theexisting wires 438 and sensor 422 illustrated in FIG. 16), electricalcurrent I_(O) (illustrated as reference numeral 484) flows from thefirst terminal 478 (to which the voltage V_(O) is applied), through theexisting wires 434 and the existing contact 424, and to the secondterminal 480 connected to electrical ground 476. Each pair 432 ofterminals in the takeover module 420 may have a current sensor 486 thatmeasures the electrical current I_(O) flowing from the first terminal478 to the second terminal 480.

The takeover module 420 may be processor controlled. A takeoverprocessor 500 may receive a current measurement 502 from each currentsensor 486. The takeover processor 500 may execute a current application504 stored in memory 506. The current application 504 is software codeor instructions that cause the takeover processor 500 to evaluate or tocompare the current measurement 502 in each circuit 426 to a thresholdcurrent value 508. When the current measurement 502 across any pair 432of terminals drops below the threshold current value 508, the takeoverprocessor 500 detects a possible intrusion event. The takeover processor500 flags the open-circuit condition 454 and obtains the terminalidentifier 456 of the open circuit from the corresponding current sensor486. The takeover processor 500 sends the open-circuit condition 454 tothe alarm controller 106 (perhaps as a message), along with the terminalidentifier 456 of the open circuit. When the alarm controller 106receives the open-circuit condition 454, the client-side securityapplication 152 may query the intrusion database 460 for the terminalidentifier 456 of the open circuit. The client-side security application152 may then send the alarm message 128 to the central monitoringstation 102 (as earlier paragraphs explained).

FIG. 29 is a schematic illustrating remote notification of the videodata 230, according to exemplary embodiments. Earlier paragraphsexplained how the alarm notification 310 may remotely notify friends,family members, or others of security events detected by the alarmcontroller 106. When the alarm notification 310 is sent to one or moreof the notification addresses 300, the alarm notification 310 mayinclude, or be sent along with, at least a portion of the video data230. When the alarm notification 310 is received, the recipient (at thethird party communications device 312) may immediately read the textualdescription of the open circuit (“basement window open”) and view thevideo data 230 captured by the camera 110. The recipient may thusimmediately verify the intrusion event. If bandwidth, packet delay, orother network factor is a concern, the alarm notification 310 may onlyinclude still images or a few seconds of the video data 230.

Again, the amount of the video data 230 may be limited. If a largeamount of the video data 230 is automatically retrieved and sent to thethird party communications device 312, chances are high that deliverywill be delayed or even fail. Exemplary embodiments may thus only send,or stream, a specified amount or duration of the video data 230 (such asten seconds). The alarm controller 106 may thus stream only a snippetthat permits quick verification of the alarm condition 126. As earlierparagraphs explained, the alarm controller 106 may retrieve and streampre-alarm and post-alarm video data 230. That is, five seconds of videodata 230 captured before the alarm condition 126 may be sent, along withfive seconds captured after the alarm condition 126 is detected. Therecipient (at the third party communications device 312) may thusquickly verify the alarm condition 126.

FIGS. 30 and 31 are schematics further illustrating remote notification,according to exemplary embodiments. Here the central monitoring station(“CMS”) server 132 may send the graphical user interface 290 to anyrecipient at the third party communications device 312. As thisdisclosure explained with reference to FIG. 16, exemplary embodimentsmay construct the graphical user interface 290 to help verify alarms.When an alarm is detected, the alarm controller 106 sends the alarmmessage 128, which routes to the central monitoring station (“CMS”)server 132. The central monitoring station server 132 generates thegraphical user interface 290 to help the agent 136 verify the alarm.When remote verification is needed, the central monitoring stationserver 132 may also send the graphical user interface 290 to therecipient at the third party communications device 312. The graphicaluser interface 290 is displayed by the third party communications device312, thus allowing the recipient to view the floor plan 292 of thecustomer's residence or business and the location of each alarm sensor108 in the floor plan 292. The recipient may also view the digitalpictures 294 of the home or business and of the possible occupants. Thelive and/or archived video data 230 may also help verify the alarmcondition 126.

The graphical user interface 290 may be sent to emergency responders.Because the graphical user interface 290 may display the globalpositioning system coordinates 296, the graphical user interface 290 maygreatly help emergency responders locate the business or residence. Thedigital pictures 294 further help location efforts, along withidentifying exterior doors, windows, and other escape routes. The floorplan 292 and the location of each alarm sensor 108 helps emergencyresponders navigate halls and rooms, and the digital pictures 294further help locate potential occupants. The graphical user interface290 may thus be sent to mobile devices (e.g., any third partycommunications device 312) to help save life and property. Indeed, thenotification addresses 300 may thus include emergency responders who areauthorized to receive the graphical user interface 290. Some individualpolice or fire members may be trusted to view very private video data230 and/or the digital pictures 294. The notification addresses 300 maythus include phone numbers and/or IP addresses of trusted emergencyresponders. Exemplary embodiments may not broadcast the video data 230and/or the digital pictures 294 to all emergency responders. Exemplaryembodiments may thus establish separate or limited notificationaddresses 300 for the video data 230 and/or the digital pictures 294,while more addresses are approved for the alarm notification 310.

FIG. 31 illustrates municipal notification, according to exemplaryembodiments. Here the security server 130 may electronically notifylocal police, fire, and other municipal entities of emergencies. When analarm is detected, the alarm controller 106 sends the alarm message 128,which routes to the central monitoring station (“CMS”) server 132. Ifthe agent 136 verifies the alarm condition 126, the agent 136 summonslocal police, fire, and other municipal entities. For example, the agent136 may instruct the central monitoring station server 132 to send thealarm notification 310 to a municipal server 520. As previous paragraphshave explained, the alarm notification 310 may include informationdescribing the alarm condition 126 (such as the alarm sensor 108, aphysical street address of the alarm controller 106, and/or any otherinformation). The alarm notification 310 routes to some municipalnetwork address associated with the municipal server 520. Here themunicipal server 520 collects the alarm notification 310 for emergencydispatch. The central monitoring station server 132 may additionally oralternatively send the graphical user interface 20 to help the emergencyresponders locate the emergency and identify the occupants.

Permissions may be required. As the above paragraphs briefly explained,some customers may not want their video data 230 shared with the localfire and police. For whatever reasons, some security customers maydecline to share their video data 230. Indeed, some customers may objectto sharing the digital pictures 294. Exemplary embodiments, then, mayfirst query the profile 320 of the occupant or home/business forpermissions. The profile 320 may be configured to permit, or to deny,sharing of the video data 230 and/or the digital pictures 294. If thecustomer permits sharing, the customer may establish separate lists ofthe notification addresses 300 for the video data 230 and for the alarmnotification 310. Again, some individual emergency responders may bemore trusted to receive and view very private video data 230 and/or thedigital pictures 294. Only these trusted individuals (e.g., theircorresponding phone numbers and/or IP addresses) may receive the videodata 230 and/or the digital pictures 294. The less-private alarmnotification 310, however, may be sent to a central dispatch or evenentire departments.

FIG. 32 is a schematic illustrating payment for emergency summons,according to exemplary embodiments. As this disclosure has explained,one of the primary functions of the agent (illustrated as referencenumeral 136 in FIGS. 30-31) is to verify alarms truly are emergencysituations. Because most alarms are inadvertently triggered, localpolice and fire departments waste time and resources responding to falsealarms. Some municipalities impose fees for each unnecessary dispatch.The agent 136, then, first tries to ascertain a true emergency existsbefore summoning emergency services. The agent 136 may call the alarmcontroller 106 to speak with an occupant, and the central monitoringstation (“CMS”) server 132 may send the alarm notification 310 tofriends, family members, and any other authorized network address 220(as earlier paragraphs explained).

Sometimes, though, verification is unsuccessful. The agent 136 may callthe alarm controller 106, but no occupant answers. Even though the alarmnotification 310 is sent to friends and family, no response may bereceived. In these situations, then, the agent 136 may immediatelysummons emergency services. If the alarm turns out to be a trueemergency, then the customer has benefitted from the emergency service.If, however, the alarm is false, then emergency personnel have beenunnecessarily summoned and financial charges may be imposed.

FIG. 32 thus illustrates a payment scheme. When the alarm is false, anelectronic debit 522 is sent. FIG. 32 illustrates a municipality server520 sending the electronic debit 522 to the central monitoring stationserver 132 in the central monitoring station 102. The electronic debit522, though, may optionally be generated by the central monitoringstation server 132. The electronic debit 522 may thus be imposed by amunicipal government and/or by the server-side security application 172.Regardless, the electronic debit 522 may include a name, address, and/orother identifier 524 associated with a subscriber to emergency services.The server-side security application 172 queries the account database134 for the identifier 524 of the subscriber, and the account database134 returns account information 528 associated with the identifier 524of the subscriber. The account information 528 may be an account numberof a savings or checking account. The account information 528 mayadditionally or alternatively be a credit card number. Regardless, whenthe alarm is false, the subscriber has pre-approved debits from, orcharges to, the account information 528 for fees imposed for falsesummons.

FIG. 33 is a schematic illustrating an external antenna 540, accordingto exemplary embodiments. As earlier paragraphs explained, the home orbusiness security system 100 sends and receives using the access pointname 120 associated with the private, wireless cellular networkconnection 124 to the private data network 104. The wireless transceiver122 preferably connects to the private data network 104 using the3G/LTE/4G wireless cellular network connection 124, but any protocol orstandard may be used. Sometimes, though, the alarm controller 106 isinstalled, mounted, or located in an area of the home or business thatlacks adequate wireless reception or coverage. A basement or closet, forexample, may have inadequate signal strength to reliably communicate.The security system 100, then, may interface with the external antenna540. The external antenna 540 may be mounted in an attic or on a roof toimprove wireless reception with the wireless access point 120 of theprivate data network 104. A coaxial cable 542 may connect the externalantenna 540 to the wireless transceiver 122 and/or the alarm controller106.

FIG. 34 is a schematic illustrating an access portal 550, according toexemplary embodiments. All communication with the alarm controller 106may require authentication in the access portal 550. Authentication maybe accomplished by providing a valid user name and password. Allcommunication towards the security system 100 may pass through theaccess portal 550 and then communicate over a secure socket layer (SSL)connection to a customer's home or business. When the customer is awayand wishes to access the video data 230 (from any cameras 110), thecustomer may first authenticate to the access portal 550. If thecustomer successfully authenticates, the customer's request flows overthe secure socket layer (SSL) connection. Likewise, when an agent in thecentral monitoring center 102 wants to access the camera 110 in thehome, the agent may first be authenticated by the access portal 550. Theaccess portal 550 may thus provide a much higher level of securitycompared to having authentication occur in the alarm controller 106.

FIGS. 35-36 are schematics further illustrating the alarm controller 106and the takeover module 420, according to exemplary embodiments. Thetakeover module 420 allows exemplary embodiments to be retrofitted toone or more existing wired sensors and/or wire contacts. As earlierparagraphs explained, conventional security systems have long used wiredcontacts and sensors to detect security events. Because these existingwired components may still adequately function for basic securityservices, the takeover module 420 provides an interface to existingwired keypads, sirens, and sensors in older installations. An existingcontroller may be removed, and the existing circuits may be interfacedto the takeover module 420. The takeover module 420 thus permits oldersecurity systems to be up-fitted without incurring substantialinstallation costs.

Exemplary embodiments thus describe professionally-monitored securityservices. The alarm controller 106 may have many standard and optionalmodules, such as:

-   -   3G Cellular Data Module (GPRS, EDGE, UMTS and HSPA+SMS);    -   24 Hour Battery Backup (Standard)    -   433/900 MHz Proprietary Wireless Transceiver Module;    -   DECT Base Station Module;    -   Takeover Module (Wired Window/Door Contacts, Keypad and Siren        Interface); and    -   Internal/External Hard Drive.        The alarm controller 106 may be wall mounted in a closet,        utility room or basement and preferably adjacent to an AC power        outlet. An external cabinet may be molded from plastic for        rugged, yet durable, use. The cabinet may be equipped with a        securely latched main cabinet door and may be equipped with a        backup battery compartment that the customer can access to        replace the battery without opening the main cabinet door. The        cabinet will support the remote installation of the external        3G/LTE/4G Cellular Data Antenna when there is insufficient        signal strength at the location of the cabinet. The cabinet will        be equipped with a tamper switch that triggers an alarm if        someone attempts to remove the cabinet from the wall when the        system is armed or when the main door or battery compartment        door is opened.

Operation is simple. When the customer puts the system into an “armed”state via a wireless keypad, Wi-Fi Touch Pad, Mobile Device or PC, theclient-side security application 152 monitors the status of wired and/orwireless sensors, such as window contacts, door contacts, motiondetectors, glass breakage and smoke/CO detector. When the system is“armed” and a sensor 108 is activated, the alarm condition 126 isestablished and the alarm message 128 communicated to the CentralMonitoring Station 102 via IP signaling over a 2G/3G/4G cellular packetdata service (GPRS, EDGE, UMTS or HSPA). If cellular packet data serviceis not available, the alarm message 128 may be sent via the customer'sbroadband data service or SMS. Wireless sensors 108 are individuallymonitored. Wired sensors may be individually monitored (star wiring) ormay be monitored as a “zone” (daisy chain wiring with multiple sensorsin a zone), which includes typically multiple sensors. The alarm message128 may include information identifying the customer's account, thesensor 108, the zone that contains the sensor, physical address, and anyother information. The customer may be automatically notified via SMS,email or a voice call when the alarm condition 126 is determined. Whenthe alarm message 128 is received by the Central Monitoring Station 102,an agent will immediately attempt to contact the customer to verify thatit is a real alarm and not a false alarm. If the agent contacts thecustomer and verifies the alarm, then the agent will contact the firedepartment, police department or EMS. In general, if the agent is notsuccessful in contacting the customer to verify the alarm condition 126,then the agent will contact the fire department, police department orEMS. During the alarm condition 126, if remote video monitoring isavailable in the customer's home, and the agent has permission to accessthe video data 230, then the agent will access the cameras in thecustomer's home to assist in verifying that it is a real alarmcondition. The agent may even have access to streaming video that wasautomatically captured at the time of the alarm and transmitted tostorage in the Central Monitoring Station.

Voice-over Internet Protocol helps verify alarms. VoIP capability, inconjunction with DECT wireless technology, may be used to providetwo-way interactive voice communication between the agent in the CentralMonitoring Station 102 and the customer in the home or business. Thealarm controller 106 may be equipped with the SIP VoIP module 190 andthe base station 212. The base station 212 wirelessly communicates withthe portable units 210 (such as DECT Intercom Speakerphone Units).During the alarm condition 126, the agent places the VoIP call 140 to aVoIP-derived line associated with the base station 212. The VoIP module190 instructs the base station 212 to auto-answer the incoming VoIP call140 from the Central Monitoring Station 102 and commands one, or more,portable units 210 to go off-hook. Then agent begins speaking throughthe portable unit 210 (e.g., a DECT Intercom Speakerphone Unit) andattempts to speak with an occupant to verify the alarm condition 126.

FIGS. 37-40 are schematics further illustrating the alarm controller106, according to exemplary embodiments. FIG. 37 illustrates exteriorfeatures of the alarm controller 106, while FIG. 38 illustrates interiorcomponents of the alarm controller 106. FIG. 39 illustrates a logicaltable of indicators that are visible on a front of the security cabinet,while FIG. 40 lists external sensors, contacts, and other components.

FIGS. 41-43 are schematics further illustrating the alarm controller106, according to exemplary embodiments. FIG. 41 illustrates thewireless transceiver 122, while FIG. 42 further illustrates batteryback-up capability. FIG. 43 illustrates the optional mass storage 114(such as a memory drive or USB stick). The alarm controller 106 may thushave an optional hard drive for locally archiving the streaming videodata 230 from the IP cameras 110. The customer is able to access andview the stored video 230 using a browser equipped device, such as a PC,Wi-Fi touch tablet or mobile device. A search function is provided sothat the customer can locate the video data 230 based on date, time ofday and/or IP camera.

When the Security System 100 is installed in a customer's home orbusiness, the electronic floor plan 292 may be created by theinstallation technician. The location of each alarm sensor 108 may beplotted or added to the floor plan 292, along with a serial number orother identifier. When the agent 136 receives the alarm message 128, theagent 136 may request and retrieve electronic floor plan 292 and locatethe physical location of the fire and/or intrusion sensors 108. Inaddition, at the time of the installation the installation technicianmay also capture the digital photographs 294 of the front, back, andsides of the customer's home or business, interior shots, and the GPScoordinates 296. This information is stored with the customer's accountinformation in the security server 130. If the customer is willing, theinstallation technician may also take photographs of all of theindividuals who may occupy the home or business. Should the agent 136summons emergency services, the agent 136 may electronically transmitthe customer's name(s), street address, GPS coordinates, and photographsof the front, back and sides of the home or business. The agent may eventransmit the electronic floor plan 292 with the locations of the alarmsensors 108. Photographs of the occupants may be sent, if permitted.

Installation of the security system 100 is simple. Conventional securitysystems require the use of a numeric keypad/display unit in conjunctionwith a complex set of procedures and numeric codes to install andconfigure the security system. Information, such as sensor zonenumbering/labeling, must be loaded via the keypad/display unit.Exemplary embodiments, however, are much simpler, for installation isaccomplished by using a web browser equipped, PC, laptop PC or Wi-Fitablet, to access the client-side security application 132. Theapplication 132 provides simple step-by-step instructions with graphicaldepictions of the equipment and procedures. Traditional keypads are notused for installation and configuration. When the installation iscomplete, a complete installation record is automatically created andstored on the alarm controller 106. In addition a copy of the electronicrecord is automatically sent to the Central Monitoring Station 102 andstored with the customer's account information.

The alarm controller 106 is installed and placed in a “wireless/wireddevice discovery” mode. The wired and wireless sensors 108 to bediscovered, such as window contacts, door contacts, motion detectors,keypads, sirens, smoke/CO detectors and IP cameras, are each placed inthe “discoverable” mode. The alarm controller 106 causes the wirelesstransceiver 122 to broadcast a device discovery request. Each sensor 108receives the device discovery request and responds. As each sensor 108is discovered, the sensor 108 is registered with the alarm controller106. After all of the wireless and wired sensors 108 have beendiscovered, the alarm controller 106 is taken out of the “wireless/wireddevice discovery” mode. After device discovery has been completed, acomplete record of all of the registered devices is stored in the memoryof the alarm controller 106, and a copy of the record is automaticallysent to a central repository (such as the security server 130) andstored with the customer's account.

Upgrades are also simple. After the initial professional installation,if the customer wants to have additional wireless devices installed intheir home (such as wireless sensors, wireless keypads or IP cameras),the equipment can be shipped directly to the customer along with simpleinstructions for installation and wireless discovery through an easy touse web interface. This can avoid having to roll trucks to installaddition wireless equipment. When the installation of additionalequipment is complete, a new complete installation record isautomatically created and stored, and an electronic copy isautomatically sent to the Central Monitoring Station 102.

FIGS. 44-49 are schematics further illustrating verification of alarms,according to exemplary embodiments. FIG. 44 illustrates a routing schemefor the Voice-over Internet Protocol call 140 to the alarm controller106. FIG. 45 illustrates the base station 212 and the portable units210. FIG. 46 illustrates communications paths available to the alarmcontroller 106, while FIG. 47 illustrates a table of operating modes andcommunications paths. FIG. 48 is a detailed schematic of the wirelesscellular network connection 124, while FIG. 49 illustrates alarmhandling and reporting.

FIGS. 50-51 are more schematics illustrating security services,according to exemplary embodiments. FIG. 50 illustrates remote access,while FIG. 51 illustrates a general network architecture.

Exemplary embodiments may be applied regardless of networkingenvironment. The private data network 104 may be a cable networkoperating in the radio-frequency domain and/or the Internet Protocol(IP) domain. The data network 104 may include coaxial cables, copperwires, fiber optic lines, and/or hybrid-coaxial lines. The data network104 may also include wireless portions utilizing any portion of theelectromagnetic spectrum and any signaling standard, as previousparagraphs explained. The concepts described herein may be applied toany wireless/wireline communications network, regardless of physicalcomponentry, physical configuration, or communications standard(s).

FIGS. 52-53 are schematics illustrating still more exemplaryembodiments. FIG. 52 is a generic block diagram illustrating theclient-side security application 152 and/or the server-side securityapplication 172 may operate within a processor-controlled device 600.The client-side security application 152 and/or the server-side securityapplication 172 may be stored in a memory subsystem of theprocessor-controlled device 600. One or more processors communicate withthe memory subsystem and execute the client-side security application152 and/or the server-side security application 172. Because theprocessor-controlled device 600 illustrated in FIG. 52 is well-known tothose of ordinary skill in the art, no detailed explanation is needed.FIG. 53 illustrates the client-side security application 152 and/or theserver-side security application 172 may alternatively or additionallyoperate within other processor-controlled devices 700. FIG. 53, forexample, illustrates that the client-side security application 152and/or the server-side security application 172 may entirely orpartially operate within a computer 704, personal digital assistant(PDA) 706, a Global Positioning System (GPS) device 708, television 710,an Internet Protocol (IP) phone 712, a pager 714, a cellular/satellitephone 716, or any system and/or communications device utilizing adigital processor 718 and/or a digital signal processor (DP/DSP) 720.The device 700 may also include watches, radios, vehicle electronics,clocks, printers, gateways, mobile/implantable medical devices, andother apparatuses and systems. Because the architecture and operatingprinciples of the various devices 700 are well known, the hardware andsoftware componentry of the various devices 700 are not further shownand described.

Exemplary embodiments may be physically embodied on or in acomputer-readable storage medium. This computer-readable medium mayinclude a hard drive, USB drive, CD-ROM, DVD, tape, cassette, floppydisk, memory card, and large-capacity disks. This computer-readablemedium, or media, could be distributed to end-subscribers, licensees,and assignees. A computer program product comprises a computer readablemedium storing processor-executable instructions for alerting of alarmsfrom security systems.

While the exemplary embodiments have been described with respect tovarious features, aspects, and embodiments, those skilled and unskilledin the art will recognize the exemplary embodiments are not so limited.Other variations, modifications, and alternative embodiments may be madewithout departing from the spirit and scope of the exemplaryembodiments.

The invention claimed is:
 1. A method, comprising: determining, by analarm controller associated with a security system, an alarm condition;querying, by the alarm controller, an electronic database for a sensoridentifier associated with the alarm condition, the electronic databasehaving electronic associations between camera addresses and sensoridentifiers including the sensor identifier associated with the alarmcondition; retrieving, by the alarm controller, a camera address of thecamera addresses from the electronic database, the camera addresselectronically associated with the sensor identifier; and sending, fromthe alarm controller, an alarm message to a destination address tonotify of the alarm condition, the alarm message specifying the cameraaddress that is electronically associated with the sensor identifier. 2.The method of claim 1, further comprising including the camera addressin a header of a packet.
 3. The method of claim 1, further comprisingincluding the camera address in a body of a packet.
 4. The method ofclaim 1, further comprising receiving a call to verify the alarmcondition.
 5. The method of claim 1, further comprising sending a textmessage to notify of the alarm condition.
 6. The method of claim 1,further comprising sending video data associated with the cameraaddress.
 7. The method of claim 1, further comprising retrieving videodata having an association with the camera address.
 8. An alarmcontroller associated with a security system, the alarm controllercomprising: a hardware processor; and a memory device, the memory devicestoring code, the code when executed causing the hardware processor toperform operations, the operations comprising: determining an alarmcondition associated with a sensor identifier; querying an electronicdatabase for the sensor identifier, the electronic database havingelectronic associations between camera addresses and sensor identifiersincluding the sensor identifier associated with the alarm condition;retrieving a camera address of the camera addresses from the electronicdatabase, the camera address electronically associated with the sensoridentifier; and sending an alarm message to a destination address tonotify of the alarm condition determined by the security system, thealarm message specifying the camera address that is electronicallyassociated with the sensor identifier.
 9. The alarm controller of claim8, wherein the operations further comprise including the camera addressin a header of a packet.
 10. The alarm controller of claim 8, whereinthe operations further comprise including the camera address in a bodyof a packet.
 11. The alarm controller of claim 8, wherein the operationsfurther comprise receiving a call to verify the alarm condition.
 12. Thealarm controller of claim 8, wherein the operations further comprisesending a text message to notify of the alarm condition.
 13. The alarmcontroller of claim 8, wherein the operations further comprise sendingvideo data associated with the camera address.
 14. The alarm controllerof claim 8, wherein the operations further comprise retrieving videodata having an association with the camera address.
 15. A memory devicestoring code which when executed causes a hardware processor to performoperations, the operations comprising: determining an alarm condition byan alarm controller associated with a security system; determining asensor identifier associated with the alarm condition; querying anelectronic database for the sensor identifier, the electronic databasehaving electronic associations between camera addresses and sensoridentifiers including the sensor identifier associated with the alarmcondition; retrieving a camera address assigned to the alarm controllerof the camera addresses from the electronic database, the camera addresselectronically associated with the sensor identifier; and sending analarm message to a destination address to notify of the alarm conditiondetermined by the security system, the alarm message specifying thecamera address.
 16. The memory device of claim 15, wherein theoperations further comprise sending video data associated with thecamera address.
 17. The memory device of claim 15, wherein theoperations further comprise retrieving video data having an associationwith the camera address.